SCR #3670     XNLIB.XNLIB     - rel3_ver3_xnlib_rel01_160128
28-JAN-16     XNLIB.XNLIBEN   - rel3_ver3_xnlib_rel01_160128
              XNLIB.XNLIBER   - rel3_ver3_xnlib_rel01_160128
                                (relinkable)
              XNLIB.XNLIBN    - rel3_ver3_xnlib_rel01_160128
              XNLIB.XNLIBR    - rel3_ver3_xnlib_rel01_160128
                                (relinkable)

           Reference: 2199833

           Symptom:
              When trying to start a 7.4 TSS process running XNLIBN as
              a library, they see the following log message and the
              process doesn't start:

              $BASET1.DE74CNFG.dalci $baset1.DE74cnfg -ai TSS 
              Process Creation Error 66, detail 5, on UL: 
              \TSYT2.$BASET2.XNLIB.XNLIBN 
              DALCI terminated by error. 
              *ERROR* PROCESS_CREATE_ Error: 66,5

            Problem: When creating XNLIB for XPNET 3.3, XNLIBN and
              XNLIBR were both incorrectly created with a float type
              of IEEE_FLOAT instead of TANDEM_FLOAT.

           Change: Created $DATA01.U33XLIB.BUILD01 and modified to
              correctly create XNLIBN and XNLIBR.

           Implementation:  Since XNLIB<xx> can be run as a user
              library, do the following only after taking appropriate
              action to avoid library conflicts.

              Install the new XNLIB files on the XNLIB subvolume.

              If using an Itanium NonStop machine (NS-Series),
              accelerate appropriate files using the following OCA
              macros:

                  - XPNET.OCANLIB   (for XPNET.NETLIB)

                  - XNLIB.OCAXNLIB  (for XNLIB.XNLIB)

              If using an X.86 NonStop machine (NS-Series),
              accelerate appropriate files using the following OCAX
              macros:

                  - XPNET.OXANLIB   (for XPNET.NETLIB)

                  - XNLIB.OXAXNLIB  (for XNLIB.XNLIB)

              Application processes which use XNLIB<xx> as a run-time
              library must be stopped and restarted in order for the
              new library to take effect.  Application processes which
              bind one of the above libraries must be re-compiled or
              re-bound with the new library.


SCR #3673     XNLIB.XNLIBEN   - rel3_ver3_xnlib_rel02_160309
28-JAN-16     XNLIB.XNLIBEN   - rel3_ver3_xnlib_rel02_160309
              XNLIB.XNLIBER   - rel3_ver3_xnlib_rel02_160309
                                (relinkable)
              XNLIB.XNLIBN    - rel3_ver3_xnlib_rel02_160309
              XNLIB.XNLIBR    - rel3_ver3_xnlib_rel02_160309
                                (relinkable)

           Reference: Internal

           Symptom:
              When trying to start an EPS process using XNLIBEN as a
              library, they saw unresolved externals for the MHDR
              routines.  Here are just a couple:

              *** RLD ERROR ***: Unresolved Text Symbol
              MHDR_SET_CONTROL_FLAG in file
              \OMA3T05.$HERMIT.SAILORD.FNSIDLLO.

              *** RLD ERROR ***: Unresolved Text Symbol
              MHDR_GET_BROADCAST in file
              \OMA3T05.$HERMIT.SAILORD.FNSIDLLO.

            Problem: When creating XNLIB for XPNET 3.3, XNLIBEN was
              incorrectly created with INTERPOSE_USER_LIBRARY OFF.

           Change: Changed INTERPOSE_USER_LIBRARY to ON and the
              process started fine.

           Implementation:  Since XNLIB<xx> can be run as a user
              library, do the following only after taking appropriate
              action to avoid library conflicts.

              Install the new XNLIB files on the XNLIB subvolume.

              If using an Itanium NonStop machine (NS-Series),
              accelerate appropriate files using the following OCA
              macros:

                  - XPNET.OCANLIB   (for XPNET.NETLIB)

                  - XNLIB.OCAXNLIB  (for XNLIB.XNLIB)

              If using an X.86 NonStop machine (NS-Series),
              accelerate appropriate files using the following OCAX
              macros:

                  - XPNET.OXANLIB   (for XPNET.NETLIB)

                  - XNLIB.OXAXNLIB  (for XNLIB.XNLIB)

              Application processes which use XNLIB<xx> as a run-time
              library must be stopped and restarted in order for the
              new library to take effect.  Application processes which
              bind one of the above libraries must be re-compiled or
              re-bound with the new library.